Membergroup picker uses logged in CMS user's account. A Mistake?

[smarshallsay]

Hi! Thanks for all your hard work with this pack. I'm a big fan!
One little stumbling block I came across recently was to do with membergroups. We'd use a picker on a page so that you could restrict a page to people with a specific membergroup, however if the editor did not have access to view members and member groups then the picker would throw an error when the page was loaded in the CMS and return no items. The problem being that the page could still be saved by that person but of course it would be saved with a blank list of member groups and remove restrictions for that page!

Using a datalist and member groups as the data source does return the list correctly even with a user that would not normally have permissions to see members / groups (i.e editor).
I wonder if the method used for getting the data for 'member group picker' should be updated to be non user permissions dependent also?