I am not an expert on the whole infrastructure stuff and not sure how all of this IOCManager works to be honest and neither the maintainer of the project. But shouldn't all of these loggers be:

private static readonly

so that we wouldn't need to create a new logger on every object instantiation?

I guess maintainers may want to comment if it makes sense to make all of them private static readonly

Ah, I checked the implementation of LogManager and saw that it actually caches loggers by name which makes sense to be honest, so strictly speaking we are not allocating a new object, though I guess every object that contains logging will have extra 3 fields. I guess we can definitely move string one to be static to optimize at least that. Not sure about the other ones, as I guess we pay the cost of 16 bytes per logged object in memory to make the logging testable?

In the end I guess none of this may matter at this point as I saw other places where static optimization may be made but I guess IOCManager complicates the actual ability to use static variables.

forgot to post this:
Due to nearly identical code behaving differently within different regions, I have used multiple patterns. This is roughly where I targeted the patterns.

• static + (log on critical fail only)
• full injection (managers)
• lazy singleton (multiple log calls on the same object)

There was a lot of trouble with null deref segfaults (and may still be)