I don't know that you'll be able to fix it, particularly without the details of how the "standard audit dates" are maintained.
It seems like this is an integrity check to make sure that between the time a row is read and it is updated, no other changes take place. If that is true, you wouldn't want to get around it. If, for example, you read the row and the value was 10, you intended to add 2 to that value, but in the meantime someone else updated the value to 20, you presumably wouldn't want to overwrite that new value with 12.
How long is the delay from the time you read data to the time you first update it and last update it. You said "I update the table from a number of sources with several statements." How do those UPDATEs affect the audit dates?
SQL DBA,SQL Server MVP(07, 08, 09) Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them.