I think you're missing that some people do odd things with their IPs as well, like have one ASN and 35 different sites where they connect to their upstream Tier69.net all with the same ASN. This means that their 35 offices/sites will each need a /32, not one per the entire asn in the table.
People who are doing that have not read the definition of the term ASN and there is no reason that the community or public policy should concern itself with supporting such violations of the RFCs. An AS is a collection of prefixes with a consistent and common routing policy. By definition, an AS must be a contiguous collection of prefixes or it is not properly a single AS. Using the same ASN to represent multiple AS is a clear violation.
And they may use different carriers in different cities. Obviously this doesn't fit the definition that some have of "autonomous system", as these are 35 different discrete networks that share a globally unique identifier of sorts.
It doesn't fit the RFC definition of AS. Therefore, there is no reason to support such usage on a continuing basis. You violate the RFC's you takes your chances. Owen -- If it wasn't crypto-signed, it probably didn't come from me.