I just ran into a side effect of it. The comment says:

	"IMPLEMENTATION NOTE: do not use CaseSensitiveOrder because it is 
broken for WideString
	This is a temporary work around until Wide CaseSensitiveOrder search is 
fixed
	Code should revert to:
	caseSensitive
		ifTrue: [^ self findSubstring: key in: self startingAt: start 
matchTable: CaseSensitiveOrder]
		ifFalse: [^ self findSubstring: key in: self startingAt: start 
matchTable: CaseInsensitiveOrder]"

I'm wondering if we can fix this issue now?

Cheers,
   - Andreas