Just thought of it again.

If we make the quicksort procedure virtual protected instead of private, it would be easy for anyone who needs it to derive a stringlist class in which quicksort makes the pivot choice without using the random routine. To avoid the performance penalty of the virtualization, the same trick as for the exchangeitems procedure could be used (though I doubt it would make a relevant difference).