"apply" arguments to new view instead of "call"

arguments pseudo-array is not a suitable parameter for a view's initialize method
Avoid accessing destroyed contexts in loop

Dispatch globally can cause certain events to close a view with bound context. This causes the destruction of the bound context. If this context has not yet been reached by the _.each loop that triggers the event on all contexts, an attempt will later be made to execute "context.vent.trigger" on a destroyed view and all further processing will abort on a "trying to access vent of undefined" error for that view.
code properly beautified
added missing semicolon
Added a test

to ensure that when contexts are all processed in sequence to trigger the event on each one, the destruction of a yet unprocessed context does not cause the program to attempt to trigger the event on it (as it no longer exists...) when the loop reaches it
Merge remote-tracking branch 'origin/patch-2' into patch-2
Added a test

Ensure that when a constructor is wrapped by the resolver  by the _wrapConstructor method, the initialization parameters used when instantiating the resulting class can be processed just as they were by the original unwrapped class (i.e. apply arguments to wrapped constructor instead of "call"ing the constructor with the arguments object)
Merge pull request #56 from mmikeyy/patch-3

here's the test
Merge pull request #55 from mmikeyy/patch-2

Avoid accessing destroyed contexts in loop
Merge pull request #51 from creynders/fix_51

BUG: Singleton (backbone) instances resolved twice
Add testing of #51
Fix #51, double resolution of singleton dependencies
Merge branch 'master' into fix_51
See #51, resolve dependencies before calling initialize