[nem-en] ManagerClass.Instance == pain!

[vc]

> I have done some more refactoring, but I think it is not entirely
> possible to eliminate ManagerClass.Instance without more performance
> loss 

What problem with performance?


> and breaking much of API and making its using harder. Moreover,
> it would in general require all code quotations to be used only where
> special "compiler context" is available, so requiring macro writers to
> pass this context to every utility function they use.

I thin, all utility function need convert into method of this context. It
will be useful for IDE support (code completion).

> Considering it, why ManagerClass.Instance is so bad for you? 

In IDE may be many Managers instance. And all calls to it members need wrap
in code which initialize ManagerClass.Instance. In some case one instance of
Manager may call another instance. Track correct value of
ManagerClass.Instance very hard.