This is a situation I find quite frustrating, which seems to be happening to me a lot lately.
I will answer a question. After pondering it, I may think of some additional points.
Later I will go back and fix some typos.
Then the OP will post some or all of his or her data. I will add some displays or other analysis, or maybe just post some comments based on some analysis of their data.
Then the OP may make a number of comments on my answer, with followup questions. Other people add more questions.
Responding to those sometimes requires many changes to my answer (even if I'd like to respond in comments, often my answers are quite extensive and involve research - finding papers, doing simulations and so on). The responses are often much too long for a comment.
As a result, to produce a good responsive answer tends to take a large number of edits over a couple of days, sometimes several edits in quick succession (respond to OP, respond to other people, notice one or more responses to my responses requiring further edits).
At least three times recently I've seen good answers I've invested many hours in polishing turn community wiki, when they really aren't community wiki - I've just been making a better, more responsive answer in multiple stages.
It's a major turn off to fixing mistakes, to putting in illustrative graphics when the data becomes available, to finding more relevant research and to responding to followup questions. That is, it puts me off giving better answers, when that time could be invested elsewhere.
But I also don't want to be bothering moderators to say 'please unwiki this' several times a week.
Is it possible to turn down - even just a little - how sensitive CV is to edits to answers from one person?
Is this something worth pursuing? Is it something that's not likely to be easily done?
Should I just be producing less ambitious, less responsive answers?
Edit: Comment/update added 1 May 2014 (local time)
I think the recent changes to the way automatic CWing works pretty much deals with my concerns on this issue.