Now that we have denies, let's @deprecate the any macro

[gus]

The any and the empty macros are complements and were useful when we only had positive assertions. Now that we have denies we can drop the any macro and use denies.empty where we would have said asserts.any before.

Sugar for sugar's sake is just over-saturation.

[charlietanksley]

I'm working on a patch to deprecate any. I modeled the changes on the deprecated not!. Based on that I assume you want to

1. Add an @deprecated comment to the Yard documentation for the macro.
2. Add a deprecation warning for the method.

What isn't clear to me is whether the README should be updated to remove said method. You haven't removed not! from the README, so that tells me to leave it. But I would've thought you would want to remove it, so as to keep from encouraging people to use it.