Well then I guess that you did not try any commands with numbers in them yet because they should work just fine for you.
When using the regular version of VoxCommando, the Kinect will not be an issue and numbers will work as they normally would with any other microphone.
If you don't intend to use the SP version of VoxCommando you can stop reading here because there is no issue that affects you.
The number limitation is only an issue when you are using VoxCommando SP with a Kinect for Windows Language Pack as the "Specific Speech Recognizer" (i.e. with one of the speech engines designed specifically for the Kinect). Apparently these special recognizers are designed to take advantage of the specific acoustic properties of the Kinect (aka the poor scratchy sound), but they also don't include numbers for some reason. Why Microsoft introduced this limitation is a total mystery to us.
Even if you are using SP with special Kinect recognizers, then numbers will still work to some extent, if you are using English. A while ago I introduced code to convert some English numbers to use words for the phrases. The code currently only addresses payload ranges or payload lists though, not payloadXML. Also, in the case of payload lists, each alias can be only a number (not a combination of words and numbers) or it won't be converted. So you could have a payload list of 5,10, 15, 20 and that would covert all those numbers to words, but 5,10,15, big 1 would only convert the first 3 numbers, and not "big 1".
I probably could add the option of converting numbers to words for payload XMLs as well but there might be a performance hit for large payloads such as with music libraries.