@Ron: Yeah sure, at one time the Earth did not even exist, too :D
The point is, a "bugfix" statement in open source code means just that: it has been fixed... a very long time ago. Not to mention that the memory leak that existed when changing a lot of options came from the WP core function and not the plugin itself, so any extension following the same path would have had to get around the same wall.
I don't get your point about volunteers. I'm a volunteer too, and easily reachable. Volunteers can refrain from stating judgements about third-party plugins they did not even try out. I have no idea whatsoever on what other solutions around are worth, because I did not try them, especially the commercial ones. I guess they are just great and I respect the people that developed them. But not knowing them, I just avoid giving any kind of judgement. Users of WP-hosted extensions can give stars to rate the actual usefulness of a plugin, they should know because they're actually using it. 100% of the users of this plugin have given it 5 stars. I guess that means in someway it works OK for them.
@Andrea: I don't mind, Ron is right it's hard to keep up-to-date on so many subjects. I would never even have hit on this forum thread if a potential user did not come forward on my developer's blog and ask if the plugin worked at all. So here is the opportunity for me to state that yes, it works pretty well on a few productions environments that I know about, and the latest version is even cooler because it can also replicate custom table data in addition to any WP option. (meaning some of the plugin settings that could not be replicated up to now are now available: for example, I have WPML auto-installing network-wide on a site.)
And to make it short: it's free, so the best way to know if it'll work for you is to just try it out!