Yes, all the time.
At work, I often have to clarify "No, I said 'x' because I meant exactly 'x'", which is a little annoying when one is dealing with other technical IT people, who are supposed to be precision and detail-oriented. What they do is to "read between the lines" and assume I must have meant something else. Now, if someone thinks that something other than what I said would be a better course of action, of course I am willing to listen, but when they just assume I meant something other than what I said it wastes time and energy for me to get them back on the mental track they would have been on already if they had paid attention. I will admit that I did this a couple of times when I started in the industry because I thought I knew better, but I was quickly set straight, which was easy as it is a very natural mode of thinking to me.
When I play or train baseball I get vague instructions all the time and it would have been so easy to give precise ones. At practice once we did a live running/pickoff drill where the runner was supposed to turn around toward the outfield while a signal was given to the fielders so the runner wouldn't know the play. Every other runner "knew" when they were supposed to turn back around toward the pitcher, I just stood there waiting to be told because there would be no other way I could possibly know when they were finished giving the signal, since I wasn't looking! Another time, the coach had us do a balance drill where we would make throws while balanced on one leg. He said to balance on "your throwing leg". Well, I don't have a "throwing leg", I throw primarily with one of my arms, though both of my legs are involved. What he meant was "the leg on the same side as your throwing arm". If he had said "back leg" or "posting leg" then there would be no question in my mind what he meant, but "throwing leg"? That's just completely useless as an instruction.