I can definitely see an argument for logging; particularly as relates to project and developer metrics.
But 'Bug Tracking' is used to describe much more than 'Bug Logging'. Bug tracking software packages define themselves and pitch their value based entirely on how they handle that 'everything else'.
Ergo, if you reject the 'everything else' (as the author does), you are rejecting bug tracking software.
at least that way when the bug re-surfaces, and you discover "its a bigger deal than we thought", you'll know for sure that you've seen it before