and it could cause a whole lot of implications that could even make the database to get crashed often. To be simple, database will become unstable and might cause a lot of issues.
Laughing to keep from crying... I mean, just say "This is a legacy architectural decision and there are no plans to change it." 
No need to throw any FUD into the discussion. Obviously if this were an exact Decimal (or even Integer, even the IRS doesn't care about decimal points with annual revenue) it wouldn't be any less stable!
But what's still being obfuscated in the response is this isn't rounding as humans understand it.
When you use a (single precision) Float, 932,849,000 is stored in Marketo as 932,849,020. Note the stored value has seemingly invented 20 more dollars out of nowhere. We don't call that rounding!
FYI, I'm working on a blog post (next blog release cycle, next week or so) that's going to dive deeper into this issue and probably blow some minds with things that unexpectedly no worky. 
.png)