I'll have a look to see if there is a way to assert the same things.

For your side question, if I remove a behavior and then try to call a method/finder from that behavior I get a `Undefined index` notice since the method still exists in the method map, but the behavior is no longer in the `loaded` array.

Likewise, I might have a behavior that I wish to use at runtime that has a method which clashes with an already attached behavior. Or I might (for whatever reason) need to re-create a behavior (Unload and then load it again).