> I forgot to mention : I tested this under release 3.23 
and 
> 3.30RC14 with the same output.

Unable to reproduce the issue using RC14, which should have 
fixed the problem - are you sure you aren't using RC13?