SimulationMessaging uses antipattern-version of Singleton

[CodeByDrescher]

SimulationMessaging implements both a create method, and a getInstVar method, where getInstVar is quietly vulnerable to a nullptr SEGFAULT if create isn't called.

Per proper Singleton design, create should be removed, and it's logic transfered to getInstVar.