You would be contributing to a database of errors that is examined for failure patterns. If a bunch of users get the same error while doing similar operations, then SCS can look for a fix in a future rev.
Generally software development follows the evolution of the version number of the product. In other words, if SCS were doing standard practice in the development cycle - the collection database roves to the the latest version.
Again IMO the only database of developmental errors that is being maintained is for VegasPro13 build 428. This does mean that an error that is identified in the past in VegasPro12 and that was not fixed or identified as managed by build428 - would still be in the database. BUT an error lately identified as VegasPro12 origination is not likely to be in the database today or tommorrow - until someone identifies it specifically in build 428.