Current situation

• The result event returns only the first alternative of the result
• If the result is split (continuous mode or interimResults mode), only the first bit is sent

Proposed change

• All result bits are aggregated
• For each result, the most confident match is used instead of the first (occasionally, the first match is the second-most confident instead of most confident)

I think the performance cost is negligible when continuous and interimResults are false (we just loop over a small ~10 items array), but this makes the wrapper useful in more cases including the one I need to support in my UI library.