Thanks, Lutz!
The reason it matters dates back to FP2.0 when an ascii character was used to record certain numeric values for a diagnosis. Looks as if we need to slow everything down to cater for the very occasional 63 or 42 value. The alternative in VFP Compiler is to use your own C++ function which I think is the way we'll go, redefining LIKE as per your #DEFINE to redirect to a new function that can mimic LIKE very efficiently..
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1