You are debugging a C++ application and find that a goto statement is causing erratic jumps and consequently, unexpected behavior. Which refactoring approach might be the most beneficial to enhance code readability and maintainability? 

Using goto statements can lead to spaghetti code that's hard to maintain and debug. It's considered a best practice to avoid using goto in C++. Replacing goto with structured loops or conditionals can often make the code clearer and more maintainable. While encapsulation is a good practice in general, it doesn't address the fundamental problems associated with goto. Comments can help but don't solve the root issue.