Class Container

Ensure createChild returns an instance of our new Container and not the base container

For each key in the wrapped container If it is already resolved to an instance And it that instance has a dispose method, then call instance.dispose But don't call it on this Container, since that would cause an infinite loop

Ensure keys requested in a child container use deps from that container OR a non-root parent if available Contrast with the key being resolved in the root and NOT using a dependency from the child container For example in a container hierarchy c1 -> c2 (where c2 is a child of c1) Given a key A depends on key B And c2 knows how to resolve B Then c2.get(A) should use the B from c2 and NOT a B from the root Current implementation is to ensure that A gets auto registered in the same container where we find the dependency then we can just proceed with normal resolution (super.get(A))