What scenario are you describing exactly? What exact problem are you trying to thwart?
A server containing a user's trade histories would show amounts deposited with Monero. But it would not contain the addresses those deposits came from, the Monero daemon doesn't know this.
Similarly, the user's withdrawals wouldn't be to an actual address that they could cross reference. RingCT gives people one time use addresses. But even if you were somehow not using RingCT addresses the Monero user experience had a best practice. Since you cannot follow transactions to that address over the blockchain, you cannot guarantee that it was the real destination at all. Any user should just have two wallets and transfer to one, which would have the address in the exchange's database, and then in wallet B, transfer to wallet C. I believe RingCT removes that marginal inconvenience, as the addresses themselves are one-time (but feel free to correct me here).