Extra check

In practice it doesn't happen, but better be safe at this point as the
transactions are not working correctly.

By the way: there a leak in the implementation of WeakDelegateNeedle,
I'll work on that.
Update for the shared templates

New method: SuspendDisposal
Increased template version to facilitate distinction of updated classes.

Reasoning: using closures may cause leaks, this is the probable reason
of the leak in WeakDelegateNeedle
Fixed a defect in the shared templates

Had forgot "using System.Threading;" Oops...
Updated to use SuspendDisposal

If my hypothesis this should fix the leak  is correct.

I have to review UnDispose...
Marked for review

I have to review UnDispose...
Another fix and clean up to the templates

You see how much I depend on autocomplete...
UnDispose use "tweak"

Just saved a few cycles there, I think.
It is ok to mix suspension with UnDispose...

Because UnDispose will never do something when the disposing is
suspended.

By the way: the leak seems to be fixed.
For debugging...