What are the pros and cons of Singleton and static members?

Opinion one: ( singleton )
The singleton mode has many advantages over static methods:
First, a singleton can inherit a class, implement an interface, and a static class cannot (can integrate classes, but cannot integrate instance members);
Second, the singleton can be delayed initialization, static class generally in the first load is initialized;
Again, the Singleton class can be integrated, and his method can be overwritten;
Finally, perhaps most importantly, a singleton class can be used for polymorphism without forcing the user to assume only the unique instance. For example, you might want to write only one configuration at the beginning, but later you might need to support more than one configuration set, or you might want to allow users to load a configuration object externally from an external file, or write their own. Your code does not need to focus on the global state, so your code will be more flexible.

Opinion two: ( static method )

objects produced in a static method are freed as the static method finishes executing, and the class where the static method resides is not instantiated when static methods in the class are executed. If you are using Singleton, the only instance that is generated will always be in memory and will not be purged by GC (because static attribute variables are not purged by GC) unless the entire JVM exits. I thought about it for a few days, and I wrote the code myself to do an experiment.

Point three: (good! )
because of the DAO initialization, will be compared to the system resources, if the static method to take, will continue to initialize and release, so I personally think that if there is no more complex transaction management, with Singleton will be better. Personal opinion, welcome you master correct.

What are the pros and cons of Singleton and static members?