Recently i was pulled in to try and save a project that was headed out the door in not so good shape and dealing with GMarkers and linked polygons was one of the more convoluted scenarios in the code. The existing workflow and 'logic' did not allow for an agile redesign of that (or any other) aspect of the project. So I dealt with it. or around it as it were, but it seem to me that there was a much easier and cleaner way to accomplish that task.
So.... I have had a bit of time on my hands and got to thinking about that and started fleshing out a library of google maps objects.
There are some who may have certain questions so let me answer them: No. It is all new, it is all mine (and whomever else wants it under dual MIT and GPL license). I could never write anything that looks like the code you apparently find acceptable. lmao.
I have released the first component, mapObjex.mapMarker, on my site and at googlecode. It supports serialization and self managed linked radii. You can use it just like any other GMarker, tell it to have some adornments, serialize the whole thing to JSON and back again. I like it.
Memory leaks are an infamous aspect of dealing with the maps api and polygons in particular especially in IE. I have taken some initial steps at mitigating the issue but there is still work to be done. If I am missing something obvious feel free to let me know.
You can see a demo and download the code @ http://skysanders.net/code/mapObjex/mapMarker.aspx