I like the variety of responses and approaches, it shows just how serious this issue is.
Samplemodeling trombone has only a range of a minor third up and down because any more would consume even more serious CPU resources.
I also added an issue of timings of legato/gliss. transitions (and note attacks):
Is there an algorithm within Dorico that will be able to take into account the length of a legato/glissando transition and adjust timings respectively? I think this is a must, when I work with Finale I have to manually nudge note timings (with a timing articulation).
Come to think of it, this feature also has to do with notes that have a slower attack, Dorico should know to adjust those notes so that the peak/middle of the attack will fall right on the beat, instead of starting from the beat and arriving too late.