At the moment it is possible to call the iterated search in weird ways with the 'pass_bound=false' option.

A short term improvement could be to have warnings like this in the constructor:

    if (bound < EvaluationResult::INFTY && !pass_bound) {
        if (log.is_warning()) {
            log << "Warning: defined bound will be ignored, due to 'pass_bound=false'."
                << endl;
        }
    }
    if (!pass_bound && repeat_last_phase && continue_on_solve) {
        if (log.is_warning()) {
            log << "Warning: This could lead to an infinite loop."
                << endl;
        }
    }

The argument `pass_bound=false` in iterated_search seems problematic.

If the inner search has a larger bound than the outer search, but the outer bound is not passed, it is unclear what should be returned when a solution lower than the inner bound but larger than the outer bound was found.

Additionally, pass_bound=false in combination with repeat_last=true could lead to an infinity loop if the last inner search does not terminate the iterated search.

It seems unclear what the purpose of the option `pass_bound=false` is in the first place.

An easy solution would be to remove the `pass_bound` parameter of the iterated search.