I fully agree with OP & respectfully disagree with @BenBrocka - for questions with limited visibility that are highly important to the poster, the poster may check back on the post daily, refresh for new answers, and see the post count has gone up (@Ason: "Unless you're systematically viewing your questions").
"At least people are reading it, someone's sure to answer soon", they might logically intuit. But they're not aware - because it doesn't follow the commonsense point of the platform - that the amount of times your question has been viewed includes the count of how many times you yourself (the one person in the world who is definitely NOT able to answer it) have read it. I came to slowly suspect this was the behaviour before confirming it by explicitly searching, and am frustrated that I wasted a week thinking that the steady trickle of interest would eventually lead to an answer.
In my opinion this is a bug (& @Scolytus should tag it as such), since the behaviour deviates from what would be expected by common sense, and directly undermines the value of the feature. I was going to raise this issue as a bug tag before finding this post.
Users shouldn't have to implement a custom script. This shouldn't be ignored simply because it becomes irrelevant when enough other people have viewed the page to dilute the effect of self views. Given the rationale for the existing setup is memory saving (avoiding keeping a growing IP list for each question), could the compromise be that it stores a list of only the logged-in user's IP addresses? This would typically be 1, a handful at most, so shouldn't be a resource burden.
It's unclear how frequently this is an issue, since it'll primarily affect:
Users in communities which are less active (common enough)
Users who aren't aware that this is how the feature behaves (conceptually everyone, initially)
Users who don't know how to, or don't care to, pick their way through the labyrinth to find this specific post on this specific board in order to discuss this bug.