Yeah, I'd also like to see an analysis of this. I used to be an automatic 'switch to Firefox for debugging' user, but I find that the Chrome developer tools are now pretty sufficient.
a small example, not really analysis, but it does count. one of the reasons I still use ff instead of chrome for debugging is that on post requests viewing the raw source of a page requires chrome to repost to the server. ff just shows me the page/data as it came back without the repost, which can be critical in debugging stateful posts where a double post effects state.