Do you have any advice for avoiding singletons? Consider I have a singleton that does Geographical lookups and requires a substantial amount of time to load/process data mapping. This data never changes after the initial load. Would it be better to make the singleton private and to access it via a non-singleton instance of the class (or subclass) it lives in?