Add support for multitouch over separate child elements. Fixes #600

[bumbu]

This fix requires hammerjs/simulator#2

The fix is based on recalculating targetTouches based on available touches. Only touches that correspond to observable element or to its child elements are marked as targetTouches.

It may be not the best place to check for touches (or naming of targetTouches should be changed) but because library heavily relies on targetTouches it was the easiest place to make the change.

Tests pass in Chrome 37, Firefox 32, Safari 7 (OS X).
Live testing works in Safari (iOS 7).

Added 3 tests that cover following use-cases:

• Pinching and rotating
• Both touches are over child elements
• One touch is over observed element and one touch is over child element

Fixed an older test by adding a target attribute to each touch.

[jtangelder]

I'm thinking about to create also a simple 'single user' touch input handler. almost all logic in this handler is for multi-user, and could be simplified (=faster). And let user set the multi-user handler as an option.
Something for 3.1 I guess.

[DallanQ]

I just ran across this issue. I updated to the master branch and it's fixed. Thank you! Hammer.js is awesome.

[jtangelder]

Just released it in the 2.0.4 :-)