It's not clear that dropping outliers is a bad idea there. It's also not clear it's a good idea, granted.
The right way to deal with outliers is to use a method that acknowledges their existence, not to ignore them. For example, if outliers destroy your OLS linear regression, it's because your error is not normal. That means you need to do Bayesian linear regression with a non-normal error term, not just throw them away.
Of course that's usually a lot easier to do with Bayesian techniques...
signal[i] = value[i] + noise[i].
If you know that value[i] == NaN, then by all means throw out signal[i]. If value[i] != NaN, then you're better off modeling error[i], and using that model to give you information about value[i] as yummyfajitas suggests.
This is trivial to see if noise[i] == 0, but for some reason becomes progressively harder for people as noise[i] increases.
In many labs, your data is looked at very suspiciously if you don't have any outliers.
An outlier may not be thrown out without good reason. Preferably an a priori reason before you do the analysis.
Moreover, the fact that Carlos entered your restaurant may be a significant event depending on the analysis that you're attempting to do. So you need to have to have a good rationale for dropping outliers, and you should probably also watch for bias when dropping outliers that don't support your hypothesis!
If Carlos Slim actually does frequent the casino, then his attendance is an important part of understanding the situation.