usp10/tests: having numbers in the ScriptStringXtoCP tests causes unpredictable behavior

[testbot at testbot.winehq.org]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=2695

Your paranoid android.


=== WVISTAADM (32 bit usp10) ===
usp10.c:1395: Test failed: ScriptStringFree should return E_INVALIDARG or E_FAIL not 00000000

=== W2K8SE (32 bit usp10) ===
usp10.c:1395: Test failed: ScriptStringFree should return E_INVALIDARG or E_FAIL not 00000000

=== W7PROX64 (64 bit usp10) ===
usp10.c:1395: Test failed: ScriptStringFree should return E_INVALIDARG or E_FAIL not 00000000