I agree, but I hate TODOs. They're the worst form of keeping track of technical debt.
Just open a ticket! I like to have a tag/label called "debt" that I put these "TODO, bad implementation" type of problems under.
That way at least it's tracked.
Having the two-directional link between the bug and the code is quite useful, especially for what is probably the most frequent use I've seen for TODOs: "We could do this better, but the better way is blocked on circumstances beyond our control. Once those change, revisit this."
The projects I work on tend to have a very quick life cycle, so there isn't even a ticketing system in place other than the occasional post it note. There just isn't the time and the team is tight.