Something changed in VS2017 such that SingletonHolder::once_flag
was not always initialized before SingletonHolder::instance and
this caused multiple singleton instances to be created. In some
ways this was a timebomb as static initialization order is
undefined.