This appears to be a bug introduced when the pattern matching routine was replaced with a faster version. During compairison testing this was an oversight.
I have modified the routine to resolve this issue. It will be in the next build.
Thanks, Great find!
|