You're right; I should put it within the started block. Actually, no
import cases are currently handled by the warning to avoid conflicting
with "import foo as bar". This isn't really an issue, though because
using the module name "as.attribute" will give a warning.

If we were going to do this again, I would implement the warning in AST
generation, but it's far too late for that.