Increased stability and flexibility, and decreased resources consumption

Thanks for your contribution and for that I didn't have to invent things myself. However to suit my needs, I had to tweak the project. List of changes:

1. Set `services.resume.forceLogout` istead of deleteing login tokens. After deleteing login tokens collections' publication is likely to stop, so user might not even get to know that the tokens were deleted. It's the only reason I could think of when the project didn't work for me. (It might be interesting that Meteor solves the similar task the similar way)

2. Replaced multiple DB requests by requests containing arrays. This should work faster.

3. Added custom logout function Meteor.forcedLogout which anyone can override to employ custom logout logic.

4. Added loginAttempt handler which should wear off all forced logout effects.

5. Increased timeouts because querying Meteor.users every 3 seconds is too expensive. Let a DB server work for users and not for nothing.

Best,
Evgeny