remove -O force-C++, and also some inadvertently replicated code

src/script_opt/CPP/Compile.h

@@ -63,14 +63,12 @@
 // the test suite.
 //
 // Zeek invocations specifying "-O use-C++" will activate any code compiled
-// into the zeek binary; otherwise, the code lies dormant.  "-O force-use-C++"
-// does the same but generates warnings for script functions not found in
-// compiled in.  This is useful for debugging the compiled code, to ensure
-// that it's indeed being run.
+// into the zeek binary; otherwise, the code lies dormant.
 //
 // "-O report-C++" reports on which compiled functions will/won't be used
 // (including ones that are available but not relevant to the scripts loaded
-// on the command line).
+// on the command line).  This can be useful when debugging to make sure
+// that you're indeed running compiled code when you expect to be.
 //
 // We partition the methods of the compiler into a number of groups,
 // the definitions of each having their own source file:

src/script_opt/CPP/README.md

@@ -80,18 +80,11 @@ event handler pulled in by `target.zeek` replaced with its compiled version.
 
 Instead of the last line above, you can use the following variants:
 
-5. `./src/zeek -O force-use-C++ target.zeek`  
-Same as `use-C++`, but also
-warns about any `target.zeek` functions that didn't have corresponding
-compiled-to-C++ versions.
-
-Or:
-
 5. `./src/zeek -O report-C++ target.zeek`  
 For each function body in
 `target.zeek`, reports which ones have compiled-to-C++ bodies available,
 and also any compiled-to-C++ bodies present in the `zeek` binary that
-`target.zeek` does not use.
+`target.zeek` does not use.  Useful for debugging.
 
 The above workflows require the subsequent `zeek` execution to include
 the `target.zeek` script.  You can avoid this by replacing the first step with: