I agree, but in that case you are consider having a fixed period over counting pulses.In certain cases, such as frequency measurement, there is no need for a managed event handler at all - the calculation (in either timer overflow or pin state change interrupt service routine) just needs to divide number of events by time period and store the result in a variable, accessible via the managed wrapper property (locking/atomic assignments assumed). Then it is possible to avoid the delay imposed by HAL completions.
At the moment I haven't the data sheet of the MCU, but on many MCUs there is a full featured timer section, that offers period between edges, pulses within a period, etc.
That would be pretty easy, I guess, but if that is not available would be an hell.
Are you able to write/insert a sampler class as above in the N+ firmware?
I have lost any hope on the last weekend, because there's no way to cut parts of the TinyCLR or anything else...Without RVDS the N+ firmware is totally off to be open!
Mario