MidiMessageSequence and note off messages

[cpr2323]

I was going to point to the post linked below as why it might be doing something different, but I realized only the copy ctor changed, not the updateMatchedPairs call.

MidiMessageSequence copy constructor has incorrect hidden side-effect

I am manually managing the noteOffObject of the MidiEventHolder as made quite easy with the return value of addEvent (as mentioned in this post from 2012, MidiMessageSequence and updateMatchedPairs). But the copy constructor for MidiMessageSequence has a hidden side effect that breaks this, and actual produces a copy that may not be the same as the source (ie. has noteOffObject filled in, even if the source didn’t). The issue is that the copy constructor calls updateMatchedPairs(). I have a prop…