Fixing problems with collection names which have the same name as functions in native

If you have collection names which are identical to functions in the mongodb-native you will get in trouble with the changes on the db prototype (https://github.com/gett/mongojs/commit/a37030ac9376d5a4f5ce514e951d0f8127c38532 and https://github.com/gett/mongojs/commit/26d17aa20f464b54e6079cc7c9826ba854e94e34).
This small fix changes the behaviour:
If you initialize collection names with the connect they will overwrite the prototype functions.
If you use the explicit collection() you will always get the collection and not the possible available prototype function.
Merge pull request #67 from Osterjour/patch-1

Fixing problems with collections which have the same name as functions