core/inlines could use Ranges

[darobin]

It wasn't an option when the original code was written because Range support was too flimsy, but it is much better now. I think that instead of doing what it is doing now which involves creating a DocumentFragment for all matching Text nodes, building the content inside, and replacing the Text node in its parent (which I'm guessing isn't fast) we could likely use surroundContents() instead. Low priority but worth investigating.

[marcoscaceres]

I looked into this a bit... I'm not convinced. Using DocumentFragment is fine.