This question already has an answer here:
Regarding Potential Duplicates: I saw this question, which got closed as a duplicate of this question, which in turn has an "accepted" answer, but doesn't answer the question (or, the answer was revoked). So, there still seems to be no thread keeping this issue open for continued discussion or waiting for a viable resolution. There may be other potential duplicates I may have missed, however.
Today wasn't the first time I failed an audit, wanting to learn more about why a question got VTC'ed. I've failed audits by accident before too, so I'm not too torn up about having failed(—although, as the person running the SO Close Votes Reviewers chat room, it'd be pretty ironic if I got banned from those reviews :-)—but I am uncomfortable that the current system fails an auditee who clicks a button which normally functions to display more information (not cast a vote). It's as if normally, it's a Close... button, and during an audit, it's a Close button—and that makes a difference.
Preempting those who'd say that one shouldn't need information about what others are doing to make their own judgment, I don't completely disagree. But, between (1) the bias that the lightbox might cause (which, we're supposed to trust users about, as answered in the linked question) and (2) penalizing the thoughtful and the curious for wanting to know more, I feel the greater evil is the latter. (Besides, why not just show no votes, as if it were a freshly flagged question? Or, if these are pulled from real examples, just show one of the votes that was originally cast.)
Precisely because I'm always skeptical of what I presently know, when I see something that doesn't make sense, I want to find out more. When I see a question that seems just fine, I instinctively click Close, hoping the subsequent lightbox might shed some light on things, or teach me something new:
Is there a more specialized site for this question that I haven't heard of?
Is there some other, subtle reason I'm not yet aware of that this question should be closed?
Was a code sample missing previously, but filled in later? If yes, then I want to see how many off-topic votes this question received, because if it has, say, 3 such votes, and the question seems useful, I'd comment, "This question has been improved and should no longer be closed for its initial reason," to fend off its impending doom. (It only takes one more user—tired and on autopilot—or predisposed to bandwagoning—out of all exposed to the question until the votes expire.)
I think this is one of those questions asking about objective differences (not opinion-based) between the internal workings of two comparable "software tools commonly used by programmers," which is a valid question. But with the popularity nowadays of closing such questions as being about "a tool, library, or favorite off-site resource," I want to leave a comment explaining the difference to future reviewers. So let's see, how many people voted to close for that reason? (Or, was this question voted to close for something else entirely that I've missed?)
I think there might be valid grounds for closing this question. But with the advent of so many new, long-descript close vote reasons, I need to go over them again to know for sure whether I'm doing the right thing.
And so on.
I use the lightbox to make many judgments about how to review a close vote, and especially whether to leave a comment and what if so. I think it's healthy that a user should attempt to investigate the context in which a question was VTC'ed. Alas the current system discourages that curiosity. I think it's inconsistent that the Close button should mean different things in practice, and during an audit.