Can't stop cursor raycaster intersecting multiple times with the same convex object

I'm using a cursor (raycaster) to select objects in a scene by having them react to the raycaster-intersected event, and I've identified a surprising edge-case.

If the object is convex (eg, a complex object loaded from a .OBJ asset) and the raycaster passes through it multiple times then the cursor's raycaster reports all intersections, counts the intersected object once for each intersection, and as a result the raycaster-intersected event can fire multiple times on the same object for a given tick.

This may be required behaviour in some cases, but in others it may be undesirable (eg, when toggling state in the selected object, or when counting the number of unique objects (rather than intersections) intersecting the raycaster.

It would be useful in these cases to be able to select between these two behaviours with a raycaster property (something like uniqueElements: {default: false}).

I actually already have a quickly hacked-up fix for this in a custom raycaster component in my current project, and will try to work it up into a PR for consideration ASAP if there's agreement it might be useful.

• A-Frame Version: 1.0.4
• Platform / Device: Confirmed Windows/Chrome, Android/Chrome, suspected all platforms
• Reproducible Code Snippet or URL: To be added

Start at the raycaster component and the raycaster-intersected event path; the issue names no source file or test, so first trace how multiple intersections are reported for one object. Done should provide a deliberate choice between reporting every intersection and reporting each intersected object once, while preserving current behavior by default.