Hi James. Thanks for the follow-up, and for your upgrade to the latest built (from the Themeforest/CodeCanyon version). What you see here is unfortunately not something we’ve controlled ourselves; the change itself was brought about by the fact that we updated to the latest Google Maps API when we launched 2.0. (Before 2.0 we were on an old build). What you’re seeing there is a byproduct of how Google’s map API now kicks out this data.
Hope that helps and sorry I couldn’t offer up more here. If I misunderstood your request here, please let me know and I’ll adjust my response accordingly.