Extending Stroke vs Stroke test to catch all intersections

Allowing the user to supply a pre-created array of points that can hold
all collisions detected between the two shapes. The last element point
will be set to x = NaN and y = NaN to signify the end of the list of
updated elements
Extending Stroke vs Stroke hit test example

The way to use the Stroke vs Stroke hit test is further demonstrated in
this examle
Adding "fromBounds" to Stroke class

Can be used for many things, visually debugging where your objects are,
but most importantly, a quick way to do object aligned collision tests.
Check
http://forum.starling-framework.org/topic/bounds-intersect-question?replies=7#post-55365
for more details and the reasons to do this.
Fixing crashes, reducing allocations

In some circumstances, a crash could occur when Graphic was disposed but
not still part of render chain. Also, reduced allocations in getBounds
from 6 to 2
Performance update for strokeCollideTest

When compared strokes have the same parent, some optimizations were
possible
Merge pull request #1 from StarlingGraphics/master

update