I suspect you may be running into a different issue- is this sorting within a related or reverse related tag? That’s the only place the prior bug was in effect. It was addressed by basically sorting fields that we know are numeric with a sort that handles number well. Other fields use a different sort- a little less ‘natural’ in their handling of numbers, but it handles spacing a a ‘human readable’ way.
However- that only applies within related/reverse related tags- which are a bit special. If it’s the sorting of a weblog tag’s main results? You’re probably running into the fact that custom fields are defined as strings- sorting is handled by the mysql query, and since they are strings, they’re handled as such. It’s not a bug- simply a result of how custom fields work.
That said- 2.0 does add some new field types- include numeric fields. Which- will sort as numbers. In 1.6 this isn’t the case. Though there are some workarounds. Let me know if this is what’s going on- and I can point you toward some options.